Common carrier system

ABSTRACT

An on-line system and method for buyers and sellers of international container transportation services is disclosed. Specifically, the system offers importing and exporting customers the opportunity to request and select specific service patterns offered by participating carriers in the booking of full container shipments. The system includes user interfaces that allow a shipper to track and trace containers across multiple carriers and an event notifications system, which notifies the user when an event has or has not occurred.

RELATED APPLICATIONS

[0001] This application claims priority to provisional application U.S.Ser. No. 60/238,454, filed Oct. 10, 2000, whose contents are expresslyincorporated by reference.

BACKGROUND OF THE INVENTION

[0002] Today, shipping goods is a complicated business. Carriers have afinite amount of cargo space, and accordingly, shippers often negotiatewith multiple carriers to coordinate the movement of just one container.Typically to limit the uncertainty and cost of moving goods, shipperscontract with multiple carriers to provide a predetermined volume ofbusiness to each carrier at an agreed upon rate. This gives shippers theflexibility to choose from a number of different carriers to transportgoods (for example, shipping directly from Stockholm to New York, ratherthan through an intermediate location) and increases the likelihood ofmoving a container when the shipper needs the container moved whileguaranteeing individual carriers a volume of business. In practice, ashipper sequentially contacts carriers to check availability. If onecarrier doesn't meet the shipper's desires, the shipper then contactsanother contracted carrier. For example, refrigeration may be requiredand only certain carriers may handle refrigerated goods, the shipper maynegotiate with only those contracted carriers that providerefrigeration. Even if the carrier may handle refrigerated cargo, theymay not have the cargo space available to move the goods by a given day.Accordingly, even if the shipper and carriers have executed a contractprior to negotiations to move goods, shippers are still effectivelyrequired to negotiate with multiple carriers when securing the transportof cargo.

[0003] Since shippers typically contract with multiple carriers, theshipper is required to learn and understand a variety of differentcarrier idiosyncrasies. The differences between carriers is compoundedas each carrier attempts automation and/or direct booking over theinternet. Each carrier booking system (or platform) may be different inthe look and feel as well as in the process that one requests thetransport of goods. This forces each shipper to learn each carrier'splatform to effectively and efficiently book a shipment of goods. Theentire process is both confusing and time consuming for shippers.Carriers are then faced with incorrect or irreconcilable booking reportsleading to more lost resources.

[0004] Freight forwarders add yet another level to this complicatedbusiness. Freight forwarders generally coordinate the transportation ofgoods on behalf of the shippers. For example, if the shipper desiresgoods be shipped from Chicago to Tokyo, the freight forwarder, on behalfof the shipper, negotiates and/or coordinates with the carriers toarrange for the goods to be moved. Essentially, the freight forwardersprovide shippers with a service and generally do not move the goodsthemselves. Thus, freight forwarders provide shippers with analternative to coordinating transportation of goods with the carriers.Although, freight forwarders provide shippers with a valuable service,they also create inefficiency and increase shipping costs for shippersas the cost for the service of the forwarders is billed to the shippers.

[0005] Biasing results in yet another inefficiency. Forwarders mayreceive incentives to direct business to certain carriers over others.Also, as the complexity of the shipping business creates a desire forboth shippers and freight forwarders to contract with certain carriers,this desire naturally creates a bias towards the contracted carriers.For example, if a shipper wants to move goods from Detroit to Spokane,the shipper may negotiate with a contracted carrier which only movesgoods directly to Seattle. A second carrier would be needed to completethe transport from Seattle to Spokane, thus, requiring an additional legto move the goods to Spokane. However, if the shipper wasn't biasedtowards the contracted carriers, the goods may have been shippeddirectly to Spokane using a non-contracted carrier. Accordingly,shippers or freight forwarders may be creating inefficiencies by notusing all available resources.

[0006] Since shippers or freight forwarders typically move goods using avariety of carriers, tracking and tracing goods across differentcarriers is also costly. Because shippers or freight forwarders oftencoordinate transportation of goods with multiple carriers, they arerequired to learn how to track and trace goods according the specificcarrier's platform. Since shippers may have hundreds of containers beingshipped by many different carriers at any given time and want to knowthe status and related info for their shipments, both shippers andcarriers devote large amounts of resources to tracking and tracingcontainers. It is not uncommon for carriers to devote an entireworkgroup to handling phone calls from shippers requiring information onthe location of their goods. A consolidated system is needed thatpermits shippers to track shipments from a variety of carriers. Also, asystem is needed that permits tracking of a shipment across multiplecarriers.

[0007] In recent years developers have used the internet to createvirtual marketplaces that bring together buyer and sellers, runnegotiations and give companies and their suppliers the ability toreadily share information. Some attempts have been made to reduce thecost to the shipper by using the internet. One attempt was to givecarriers the ability to post published rates and discount informationfor land, sea and air bearing cargo vessels allowing customers toevaluate prices prior to booking. Another attempt to use the internet,give shippers the ability to receive a plurality of bids from aplurality of participating cargo transportation entities. These systemsmerely identify the cost of doing business with a select carrier and nomore. This does not solve the problem of having to use multiple carrierplatforms to submit the booking request to different carriers. This alsodoes not permit easy exchange of goods between carriers where multiplecarriers are used for a single shipment.

[0008] Finally, warehousing goods, transporting goods, customs brokerageand trade finance are complicated pieces of a very complicated business.Accordingly, a need exists for a more efficient system for handlinglogistics and transportation of goods.

SUMMARY THE INVENTION

[0009] The disclosure provides a method and system that enables domesticand international transportation users to handle shipping transactionsthrough a single common system through a neutral transportation portal.The system provides, among other things, transportation users withsingle point of entry for tracking cargo movements with multiplecarriers. In various embodiments, the system also gives users access toscheduling, booking requests for booking cargo across several carriersand, in some embodiments, proactive event notification.

[0010] These and other benefits will become apparent as described in thedrawings and related description.

BRIEF DESCRIPTION OF DRAWINGS

[0011]FIGS. 1a and lb illustrate the system infrastructure according toembodiments of the present invention.

[0012]FIGS. 2a, 2 b, 2 c, 2 d, 2 e, 2 f and 2 g illustrate a flowchartdepicting a booking process according to embodiments of the presentinvention.

[0013]FIG. 3 illustrates an example of a selection screen according toembodiments of the present invention.

[0014]FIGS. 4a-4 c illustrate an example of a booking request screenaccording to embodiments of the present invention.

[0015]FIG. 5 illustrates an example of a contact section of the bookingrequest screen according to embodiments of the present invention.

[0016]FIG. 6 illustrates an example of the HAZMAT screen according toembodiments of the present invention.

[0017]FIG. 7 illustrates an example of the temperature control screenaccording to embodiments of the present invention.

[0018]FIGS. 8a, 8 b, 8 c and 8 d illustrate an example of haulage andsearch screens according to embodiments of the present invention.

[0019]FIGS. 9a and 9 b illustrate an example of company search screensaccording to embodiments of the present invention.

[0020] Figures lOa and lOb illustrate an example of a search templatescreen according to embodiments of the present invention.

[0021] Figure 11 illustrates an example of a search for a booking screenaccording to embodiments of the present invention.

[0022]FIGS. 12a, 12 b and 12 c illustrate examples of track and tracescreen and result screen according to embodiments of the presentinvention.

[0023]FIG. 13 illustrates an example of the common carrier systemaccording to embodiments of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

[0024] The following description is divided into sub-sections to assistthe reader. The sub-sections include: terms; infrastructure; bookingprocess and user interface; track and trace; and event notification.

Terms

[0025] The following terms are used in the description.

[0026] Shipper—Any entity with goods to be transported. The entity maydesire the goods be transported or may be transporting the goods for adifferent entity.

[0027] Freight forwarder—An entity that coordinates the transportationof goods with a carrier or carriers for a shipper.

[0028] Carrier—Any entity that transports goods from an origin to adestination. The carrier may transport goods domestically and/orinternationally. For example, a carrier may transport goods for ashipper from Chicago to Seattle or the same carrier may transport goodsfrom Chicago to Paris. The carrier may transport goods using trucks,trains, planes, ships, and/or the like.

[0029] Carrier Platform—A carrier's computer system supporting aninterface that enables exchange of information with the carrier.

[0030] Common Carrier System—Infrastructure that supports the commoncarrier interface including data storage.

[0031] Common Carrier Interface—An interface that enables multiple usersand multiple carriers to communicate.

[0032] User—Any entity that uses the common carrier system. All usersmay have various levels of interest in using the common carrier system.The main users of the common carrier system may be shippers, third-partylogistics providers, freight forwarders, consignees, brokers, tradingportals, carriers and the like.

[0033] Booking—A reservation to transport a volume of goods from asingle origin to a single destination. The goods may vary in producttype, may be a mix of hazardous and non-hazardous, may requirerefrigeration and the like. The booking may be a single booking or maybe repetitive.

[0034] Routing Request—A query to the carrier to determine if thecarrier supports the basic transpirations of the cargo as part of thecarrier product catalog.

[0035] Booking Activity Plan—A carrier plan that encompasses the major,or milestone, activities of a shipment.

Infrastructure

[0036]Figure 1a illustrates an example of representative infrastructureaccording to embodiments of the present invention. The user 101 a-101 e,via terminals, communicates with a plurality of different carriers 103through the common carrier system 102 including server(s) 102 b-102 cand database(s) 102 a. In one embodiment, users use terminals toexchange information with the common carrier system 102. These terminalsmay be standard personal computers as are known in the art (forinstance, a computer system using a PENTIUM III processor). Inalternative embodiments, the users may use hand-held or other portabledevices as known in the art to communicate with the common carriersystem 102. Further, the communications from multiple users may bebatched together at a user's location prior to transmission to thecommon carrier system 102. Although FIG. 1a shows five users, fivecarrier terminals, one database and three servers, FIG. 1a is merelyillustrative and the number of, users and/or user terminals, carriersand/or carrier terminal, servers and databases is not in anyway limited.Furthermore, although the embodiments are described in the context of asingle system, one of ordinary skill in the art may appreciate that thedescribed functionality may be implemented across multiple systems.Moreover, a web site may be mirrored at additional systems in thenetwork and, if desired, one or more management systems or othercomputer resources may be used to facilitate various functions. Thecomputer program at the system includes appropriate screen routines forgenerating a set of screens that together comprise a user interface forthe site.

[0037] Referring to Figure 1b, illustrates, in more detail, the commoncarrier system 102. The common carrier system includes, for example andwithout limitation, servers 104 a-104 c. Server 104 a includes mailserver 105 which may be used to receive and send data via email. Server104 a also includes server 106 for receiving and sending data over theinternet. Server 104 b includes server 107 as a communication bridgebetween server 108 and servers 105 and 106. Server 107 polls servers 105and 106 for new messages, unpacks and sends the messages to server 108.For outbound polls from server 107, server 108 adds the receiver'saddress and triggers the transfer of the message. When server 107 failsto process an EDI message, an email will be sent to a predefined emailaddress. Server 108 processes EDI messages by validating the data whencalled by server 107 and translating the data into the common carriersystem layout format. For outbound EDI messages, server 108 is called byserver 109 and server 109 feeds server 108 with the outbound EDI messagein the common carrier system layout format. Server 104 b includesservers 109 and 110. Server 109 converts and loads common carrier systemlayout to a set of database tables, or vice versa. Server 109 also pollsserver 108 for any new messages, opens a connection to the database andpopulates the database tables corresponding to the EDI message type(300, 301, 315 and the like, show in FIG. 13). For outbound EDImessages, server 109 scans the database tables populated by an EDIprocessor and converts the message and then triggers server 108 toprocess the common carrier layout format. Referring to Server 110, theEDI processor is part of the server 110 that processes the EDI messagesdeposited into the database tables by 109. Server 110 scans the headerof the database table for the first unprocessed message being marked forexample as submitted. The status is then change from submitted toprocessing in the database 111 and if successful the status is thenchange to complete.

[0038] The present disclosure relates to a system and method for buyersand sellers of domestic and/or international transportation servicesrelated to the shipment of goods. The users and carriers may be linkedto the system by dial-up modem to communicate to the internet, andaccordingly, be disconnected from the system or off-line. For example,the user may use a dial-up modem and submit a booking request to acarrier through the internet and afterwards disconnect from the internetAfter the user disconnects and is currently off-line, the common carriersystem may submit the booking request to the carrier and receiveconfirmation of the booking request from carriers while the user isoff-line. In another embodiment, the common carrier system 102 mayprocess the information while the user is still connected with theinternet. This permits the user to be notified as soon as availabilityis determined for various carriers or after a reservation has been madewith the carriers by the common carrier system 102. The system andmethod offers shippers the opportunity to request and select specificservice patterns offered by participating carriers in the booking offull container shipments. The system and method includes userinterfaces, processes, computer systems, and computer-readable mediumshaving programs stored thereon. The system and method enable a user tosubmit booking requests to multiple carriers and/or track and trace thegoods using a single common carrier system and interface. The system andmethod also may be used to provide event notification.

[0039] In general, when a shipper wants to move goods, the shippersubmits a booking request to one or more carriers to which thecarrier(s) responds by accepting, rejecting, or changing the bookingrequest. A booking represents a shipper's intention to transport avolume of goods from a single origin to a single destination. The goodsmay vary in product type, may be a mix of hazardous and non-hazardous,may require refrigeration and the like. As a result, differing containertypes may be required. To accommodate differing cargo characteristics, abooking may contain one or more booking lines. The request may be madeusing a variety of different processes. The user 101 may send an emailmessage to the common carrier system 102, who processes the email andacts in response. Alternatively, the user 101 may post information to aweb site of the common carrier 102. Further, the user 101 may transmitinformation in the form of XML or EDI data sets for processing by thecommon carrier system 102. It is appreciated that a number of differenttransmission schemes may be used to forward requests to the commoncarrier system 102. The information received by the common carriersystem 102 may then forward the requests to a variety of carriers 103.The common carrier system 102 may blindly forward the request to allcarriers 103 to see who responds. Otherwise, the common carrier systemmay filter the booking request from user 101 to minimize the number ofcarriers 103 who receive the request. In addition, the common carriersystem 103 may have a routing list as specified by the user forpermitting the ordering of the hierarchy in which carriers are polledfor booking availability.

[0040] The transmissions between the common carrier system 102 and thecarriers 103 may also be in the form used by the user. Alternatively,the common carrier system 103 may translate the user's request from oneform or format into one understood by the carrier or carriers 103. Ifneeded, common carrier system 103 may add information or subtractinformation as needed for each carrier 103. For example, some carriersmay use one type of units while others use another type of units. Thecommon carrier system 103 then translates the units provided by the userfor submission to the carrier. Also, the user may have certain needs ifgoods are transported one way as opposed to another (refrigerationneeded if shipped in a container ship while no refrigeration needed ifshipped by truck or train). If so, the common carrier system 103 mayeliminate or modify the information transmitted to each carrier 103 soas to meet the needs of each carrier's platform and/or booking system. Abooking line may include a single container type, single hazardous goodsindicator, single refrigeration and a single commodity description. Whenthe common carrier system receives the first carrier bookingconfirmation massage, for example the confirmation from carrier 103 a,the system 102 may, upon the shippers request (any user using one ofterminals 101 a-101 e or other known devices like, for example, a mobilePDA), automatically generate and submit booking cancellation to othercarriers 103 b-103 e.

[0041] Alternatively, the booking request from the common carrier system102 may request information from the carriers 103 of who hasavailability for handling the proposed booking. The response from thecarriers 103 provides the common carrier system 102 with information ofavailability, shipping time frame, and other information.

[0042] In one example, an interested party, typically the shipper orfreight forwarder, enters a booking draft with high-level details aboutthe freight it desires to be shipped. Using the information entered onthe booking, the user of the system may also, via terminals 101 a-101 e,issue a routing request through the common carrier system 102 to one ormore carriers 103 a-103 e. One or more of carriers 103 a-103 e respondswith detailed routing information. The shipper may request the carrier103 a-103 e submit routing information based upon the data containedwithin the booking (place or receipt, place of delivery, etc.) Thecommon carrier system 102 enable users (via terminals 101 a-101 e or byother known devices like, for example, a mobile PDA) to submit abooking, with or without a routing request, and it may be submitted toone or more carriers 103 a-103 e.

[0043] The actual interfaces between the user 101 and the pluralitycarriers 103 handling the routing request may be determined by thetechnical capabilities of the carriers 103. Sophisticated carriers 103may provide direct online response through their internal systems. Othercarriers 103 may use the service patterns interface to store availableroutings. At a minimum, all carriers may respond to routing request viausing the common carrier system 102. Separate confirmation directed toeach user may also be made (via email, instant messaging and the like).

[0044] If the booking party 101 chooses to so specify (for example, bychecking a checkbox or similar object on the booking screen), the firstcarrier to respond with a valid response to the routing request mayautomatically be selected and the booking may be submitted to thecarrier. Otherwise, the booking party may manually select the carrierand submit the booking. It is now up the carrier to determine if theactual transport of cargo may take place (based on vessel capacity,equipment availability, etc.) and either confirm the booking, declinethe booking or make a counter proposal.

[0045] Referring to FIG. 1, after carrier 103 a confirms the booking,the user sends shipping instructions using the common carrier system 102by interacting with the common carrier interface. The information sentcontains more details about the freight, such as hazardous/refrigerationcharacteristics. Since the booking already contains the rudimentaryinformation about the care, the shipping instruction don't need tohappen at any a particular time. The carrier then sends the bill oflading based on the shipping instructions.

[0046] Finally, when a carrier confirms the booking, the carrier mayreturn a booking activity plan as part of the booking confirmation. Theplan may be stored in the common carrier system database(s) 102 a of thecommon carrier system 102 and subsequent track and trace messages may beused to measure performance (time to process bookings, per cent on timedelivery, claims, misdeliveries, etc.) against the booking activityplan.

[0047] The common carrier system enables the common carrier interfaceprovides the users with a unified booking interface and procedure whilealso providing an additional source of bookings for the carriers.

[0048] Furthermore, the common carrier system and interface enables theuser to create templates tailored for their specific needs. Accordingly,the user may quickly create template-driven booking requests withouthaving to step through the entire booking process. Also, Identifying andregistering a user's consignees, forwarders, shippers, et al., mayfacilitate the template building process and provide shipment visibilityto user's partners as quickly as possible.

Booking Process and User Interface

[0049] The description of the first embodiment is organized to showprocess flows as taken by the user. Various user interface screensembody the process flows.

[0050]FIGS. 2a-2 g illustrate the booking process from creating abooking request, using any one of the three booking methods, throughreceipt of booking confirmation. FIGS. 3-12 illustrate the variousscreens the user may encounter throughout the booking process describedby FIGS. 2a-2 g. Although, FIGS. 3-12 illustrate display screens, theparticular screen layouts are used for exemplar purposes only and shouldnot be taken to limit the scope of the embodiments in any way.

[0051] The process of creating a booking request through confirmationwill now be described, with reference to FIGS. 2a-2 g. The process maybe rearranged as needed or to accommodate faster information processing.Referring to FIG. 2a, first the user logs into the common carrier systemas shown in step 201. At step 202, the user selects a new bookingrequest. At steps 203-205, the user chooses from creating a new bookingrequest, reusing an existing booking request and creating a bookingrequest from a predefined template.

[0052] Creating a new booking request will now be described. If the userchooses to create a new booking request in step 203, then the usercontinues to step 206 and identifies the carrier and the commoditydescription details. If HAZMAT data is not desired, the user advances tostep 210 of FIG. 2b. If HAZMAT data is desired, the user enters the dataat step 208 via a pop-up window and then advances to step 210.Optionally, the user may enter contract information at step 209 in afree text field.

[0053] Referring to FIG. 2b and 2 e, at step 210, the user identifiesequipment quantity and type. If specific environmental conditions arenot desired, the user continues to step 213. If certain environmentalconditions are desired, at step 212, the user enters the appropriatedata and then advances to step 213. At steps 213-215, the useridentifies the place where the carrier responsibility for cargo beginsincluding the pick-up date and the place where carrier responsibilityfor cargo ends including the delivery date. Optionally, the user mayenter the load location and discharge location and/or specialinstructions in steps 216 and 217.

[0054] Referring to FIG. 2f, from steps 215 or 217 and if door pick-upis desired, the user advances to step 218. If not, the user advances tostep 220, door drop-off. From step 220, if door drop-off is not desired,the user advances to step 226. If door pick-up is desired, the useridentifies the address, any necessary comments, and dates at steps221-223. The user then continues to step 220. If door delivery isdesired, the user identifies the delivery address and the date forcontainer delivery during steps 224 and 225, respectively.

[0055] Referring to FIG. 2g, from steps 220 or 225, the user advance tosteps 226, and if desired, step 227. The user identifies the shipper andother shipment parties, step 226. The shipper may be the booking party.If the other shipment parties are not registered, the system may notprovide visibility. However, the system may provide booking visibilityimmediately to registered parties, steps 227-230.

[0056] After identifying the shipping party at step 236 and steps227-230, the user advances to step 231 and submits the booking requestto the system, wherein the system submits the booking request to thecarrier at step 234. The user may also reach step 234 by entering areference number and remarks during steps 232 and 233, respectively.Additionally, the user may reach step 234 by reusing an existing bookingrequest or from a predetermined template as shown in FIG. 2a, steps 204and 205. The user identifies the old booking or the template and thenupdates the routing, haulage, dates and submits the updated bookingrequest, steps 235-240. Furthermore, the common carrier system enablesentities to register via the common carrier interface.

[0057] Referring to FIG. 2c, the carrier may be alerted by the commoncarrier system, via Electronic Data Interchange (“EDI”), email, commoncarrier interface pop-up dialogue box and the like, step 241. CSR entersthe booking into the carrier's booking system and confirms or countersthe booking origin, POL, POD, destination, load date, discharge date,vessel voyage and the like in the common carrier system, steps 242-244.If door delivery was requested, the CSR enters carrier outboundcontainer P/U, if not, the CSR enters cutoff date at origin in thecommon carrier system, steps 245-247. The booking is confirmed,countered or rejected and returned to the common carrier system. Thecommon carrier system alerts the user of the reply from the carrier,steps 248-249. The user takes no action, and thus, accepts the bookingas is, cancels the booking request or amends the booking request, steps250-252. If the user cancels or amends the booking, the carrier isalerted and accepts, declines or changes the booking in the carriersystem and updates changes in the common carrier system. The commoncarrier system submits the response to the user via EDI, email, commoncarrier interface pop-up dialogue box and the like, steps 253-256.

[0058] As illustrated in FIGS. 2 and 3, the user, after login, has anumber of options to navigate through the common carrier system. Tocreate a new booking request, the user selects the “Booking” menu option301. This menu option enables the user to create a new booking request302 or search for an existing booking request 303. If the user needs tocreate a new booking request, then the user has three options: (1)create a new booking request from scratch 304, (2) reuse an existingbooking request 306 and (3) create a booking from a predefined template305 as shown in FIG. 3.

[0059] Creating new booking request will now be described with referenceto FIGS. 3-10. Upon selecting the “from scratch” menu option 304, shownin FIG. 3, the user is linked to the new booking request screen, shownin FIG. 4a-4 c. The new booking request screen is divided into severalsections: (1) carrier selection 401, cargo information 402, containerinformation 403, routing information 404, booking parties 405 a-405 d,and additional information 406. Each enables the user enter information.Although all sections are shown on a single screen, this is merely anexample and should not be taken to be limiting in any way. For example,each section maybe shown using a separate screen. Each of these sectionswill now be described with reference to FIGS. 4-9.

[0060]FIG. 4a shows the carrier selection section 401 of the bookingrequest screen. To enter information in this section, the user clicksthe “Select Carrier” drop-down menu 407 and identifies which registeredcarrier may be sent in the booking request. If desired, the user mayenter a contract reference, the quote number or TLI in the contractreference field 408. Optionally, the user may enter a PO number into thePO number field 409. If desired, the user may attach additionalreference numbers by clicking the “Additional Reference Numbers” button410 which would link the user to the additional reference screen asshown in FIG. 5. The user may enter a reference type by using adrop-down menu 501. Also, the user may enter a reference value in thereference value field 502, add a reference by clicking the “Addreference” button 503, and/or may remove reference(s) by clicking the“Remove Reference” button 504. After the user has entered theappropriate data for each object, the user clicks the “Done” button 505.

[0061] Referring to cargo section 402 of FIG. 4a and FIG. 6, the usermay enter the commodity description in the description field 411, alongwith the total cargo weight in the total cargo weight field 412. Theuser defines the total cargo weight as being either metric or imperialusing drop-down menu 413. If the commodity is hazardous, the user mayclick the “Hazmat” button 414. This button links the user to thehazardous material settings window shown in FIG. 6. The common carriersystem supports multiple hazardous IMO classes per commodity. Forexample, a commodity “Car Parts” may hold two hazardous line items, onefor seat belt tensionless, and another for air bags. The user selectsthe appropriate hazardous class from the “IMO Class” drop-down menu 601and then user enters the proper shipping name and the four digit UNnumber in the un number field 602. Additionally, the user may enter thepacking group, flash point, emergency contact details and furtherspecification for each IMO line item in fields 603-606, respectively.Once all the details for one IMO class have been entered, the userclicks “Add IMO Class” button 607 to associate the hazmat details withthe commodity. After the user is finished inputting of the hazmatdetails for all the commodities the user clicks the “Done” button 608.

[0062] Referring to the container information section 403 of FIG. 4a andFIG. 7, the user enters the number of containers they wish to request inthe quantity free text field 414. With the “Type/Size” drop down menu415, the user identifies the kind of equipment they wish to request.Some carriers do not support some types of equipment. To help the user,carrier-specific equipment may be identified in the drop down free textliterals. The user identifies at least one container for each bookingrequest. In the container information section, the user has the optionof selecting the “Temperature Control” button 416 to bring up therefrigeration details pop-up window as shown in FIG. 7. The user may setthe booking temperature as Fahrenheit or Centigrade by clicking the ° C.or ° F. buttons 701 and 702, respectively; set the temperature usingfield 403 and clicking either button 404 or button 405; set theventilation in cubic meters per hour using field 706; set the humiditysettings as a percentage using field 707; and provide additionalcomments using field 708. After enter the appropriate setting, the userclicks the OK button 709 to save the environmental settings.

[0063] Referring to the routing information section 404 of FIG. 4b andFIGS. 8a, 8 b, 8 c, and 8 d, the user enters the routing details for thebooking request. The user enters the place of origin in field 417 (placeof origin is the location where the carrier's responsibility for thecargo begins); the requested date at origin in fields 418 a-418 c (thedate when the carrier takes responsibility for the cargo); the requestedvessel voyage in field 419; and the destination in field 420 (thelocation where the carrier's responsibility for the cargo ends).Optionally, the user may enter the load and discharge locations infields 421 and 422. If the user desires to have the product picked-up,the user clicks the “Door Pickup” button 423 which links the user to thedoor pickup details screen shown in FIG. 8a. The user then enters theoutbound empty equipment drop-off date and time in fields 801 a-801 d,the outbound stuffed equipment pick-up date and time in fields 802 a-802d, and additional door pick-up details, including company name, contactdetails, telephone, and the pick-up address in fields 803-806,respectively. After entering the appropriate information, the userclicks the “Save Haulage” button 807 to update. Additional haulagedetails may include hot load, equipment drop-off schedules and the like.If the user desires to have the containers delivered, the user clicksthe “Door Delivery” button 424 which links the use to the haulagerequirements delivery screen shown in FIG. 8b. The user enters theinbound empty equipment availability date and time in fields 808 a-808 dand additional door pick-up details, including company name, contactdetails, telephone, and the pickup address in fields 809-812,respectively. Followed by the user clicking the “Save Haulage” button813 to update. Additional haulage details may include hot load,equipment drop-off schedules, and the like.

[0064] Optionally, the user may search to find the common carrier systemfor the registered locations of the place of origin, load and dischargelocations. Several locations in the booking screen may be registered(non-free text) locations. To assist the user with identify theselocations, the user may link to the search screen for assistance byclicking any of the buttons 425-428. The user may enter any combinationof city, state, and country in fields 814-816 and press the searchbutton 817 of FIG. 8c. The common carrier system displays the resultsshown if FIG. 8d. The user clicks on the correct location to select it,for example click on line 818, 819 or 820, or clicks the “Start Over”button 817 to return to the search screen.

[0065] Referring to the booking parties section 405 of FIGS. 4b-4 c andFIGS. 9a, and 9 b the user enters the booking parties, thus, identifyingthe parties associated with the booking request. The booking party maybe identified as any one of shipper, export forwarder, consignee,contracted party and the like. Either the shipper or the exportforwarder is identifiable on the system. To receive cargo visibility assoon as possible, the identified parties may be registered on the commoncarrier system. The parties may register with the common carrier systemusing the common carrier interface. If booking parties are not selectedin this section, they may not be able to view the booking until theircontact information is retrieved from the BL. That is, booking partiesidentified by the user may be capable of viewing the booking so long asthey were a party selected by the user and they are registered with thecommon carrier system. Registration may be completed using the commoncarrier interface. Using fields 429 a-429 d, 430 a- 430 d, 431 a-431 d,432 a-432 d and 433 a-433 d as shown in FIGS. 4ba and 4 c, the user mayenter the name, address, reference, contact, and telephone number of thebooking parties. So long as the party is registered, that party may viewthe booking.

[0066]FIG. 9a and 9 b show a company search window for the user'sconvenience. When the user clicks the “Search” buttons 434 a-434 d fromany booking party section, the user is linked to the company searchpop-up window. The user enters the company name in the window in field901 and clicks the “Search” button 902. The user then clicks on thedesired company. An example list is shown in FIG. 9b.

[0067] Referring to the additional information section 406 of FIG. 4c,if desired, the user may provide additional information by entering theadditional comments in the additional information field 435. This areais free text and may hold, for example, details not be captured in theexisting booking screens. Comments, for example, may include drop andpick; hot load, drop-off/pick-up schedules, HAZMAT details and the likeshould be entered here.

[0068] Once the user entered all initial data, the user may send thebooking request, save the booking request as a draft or save the bookingrequest as a template by clicking one of the appropriate buttons436-438. If the user sends the booking request, the carrier selected bythe user may then be alerted by the common carrier system and reply tothe user's booking request. If the user saves the booking request as adraft, the user may at a later time complete the booking request andsend it to the carrier and/or save the booking request as a template.

[0069] Creating a booking request from a template will now be described.Referring to FIGS. 1Oa and 10 b, to create a booking request from anexisting template, the user starts from any of the common carrier systemscreens after login and selects the “New” 302 menu and then the “FromTemplate” menu 305 from the booking menu 301 as shown in FIG. 3. Thisaction links the user to the template search screen. The user enters atleast one of the template name, origin/destination, cargo description,company, and carriers in fields 1001-1006, respectively, to find thebooking template. Once the user enters the data, the user clicks the“Template Search” button 1007. The common carrier system generates alist of any template that matches the search. The user selects thedesired template. An example list is shown in FIG. 10b. If desired, byclicking the “New Template Search” button 1008, the user may add orremove criteria to limit or broaden the search. Once the user finds theappropriate template, the user may, for example update the datesassociated with the booking along with additional booking requestfields. The user may save the template and/or submit the booking requestto the carrier. If desired, the user may delete the template, forexample, by checking a box, like 1010, and clicking the “DeleteTemplate”button 1009.

[0070] Reusing an existing booking request will now be described.Referring to FIG. 3 and FIG. 11, starting from any of the common carriersystem screens after login, the user select the “New” menu 302 and then“From Existing Booking” menu 306 from the booking menu 301 of FIG. 3.This action links the user to the search booking screen shown in FIG.11. The user inputs data in at least one of references, booking number,ocean carrier booking number, bill of lading number, container number,booked vessel, booked voyage, latest vessel, latest voyage, cargodescription, location, dates, company, carriers, cargo and event fields1101-1112, respectively. The user selects the desired template from thereturned list of old bookings, or performs another search. Once the userfinds the desired booking request, the user updates the booking andsubmits and/or saves the booking request.

[0071] The common carrier system is capable of developing forms for thecommon carrier interface which help users capture their tradelanes,commodity and equipment requirements, routing, and booking partydetails. These forms enable the common carrier system to create customerspecific booking request templates. In most cases, a booking templatecapture the majority of fields described above, and worksheets groupthese fields into easily understood sections.

[0072] Bookings may be made, for example, through the common carriersystem user interface, Electronic Data Interchange and the like. EDItransmission pass through the common carrier system to allow commoncarrier system functionality to be used. For example, track and tracefunctionality require the booking EDI transmission pass through thecommon carrier system. Booking made via the common carrier system userinterface may be made from scratch of facilitated by means of previouslysaved data in the form of templates or previous booking as describedabove.

Track and Trace

[0073] This embodiment enables the user to track and trace only byidentifying container as opposed to tracking and tracing by identifyingboth carrier and container. That is, the user does not need identifywhich carrier is transporting their container. Accordingly, the commoncarrier system enables the user to track and trace containers acrossmultiple carrier platforms from a single system, the common carriersystem.

[0074] The common carrier system facilitates track and trace informationwithin the confines of a carrier's responsibilities. The boundaries fortracking a shipment directly reflect the associated route and servicepatterns supporting that container's movement. Applicable common carriersystem users, via terminal 101 a-101 e of FIG. 1, have the ability toview the execution status of the shipment(s) on an as-needed basis. Thebooking activity plan defines the carrier's intended method and timesfor transporting a container from its origin to its final destination.This provides the benchmark for determining whether events that shouldhave occurred have not. The common carrier system 102 alerts the partiesof non-confirmation. The carriers offer event reporting against themilestones contained in the booking activity plan. The system operatesusing standard event codes and standard event messages. In other words,carriers 103 may update the common carrier system 102 using commonreporting information. Alternatively, the common carrier system 102 mayreceive tracking information from each carrier in each carrier's nativereporting format. The common carrier system 102 then extracts desiredinformation from the carrier's tracking information and formats it intoa style that is extensible to the user 101. Also, an intermediate formatmay also be used to internally store the tracking information from eachcarrier in the common carrier system 102. The system may log when eventmessages are received (in local time) to enable carrier performancemonitoring.

[0075] To use the track and trace function, the user request a bookingwith a common carrier registered carrier using the common carrier systemas outlined above. The carrier confirms the booking request and submitsa booking activity plan for the booking at the same time. A singlebooking supports a single booking activity plan. The booking may consistof multiple container movements. The booking activity plan may be usedto support track and trace information at the container level. Thebooking activity plan may provide greater information than a servicepattern, since each main leg may be broken down into actual transportmodes, transshipment locations and interim arrival and departuredate/times.

[0076] Once the carrier submits the booking activity plan the containermay be tracked and traced. The carrier submits the track and traceevents to the common carrier system either by EDI or via a commoncarrier system user interface. Carriers may continue to use their owncoding convention when submitting events by using EDI translator. EDItranslator translates carrier event codes and message formats into acommon carrier system neutral format. The common carrier system mayrecord when a shipment has departed and arrived at the various locationand record when business processes or non-conformances occur. The commoncarrier system may also record the date and time when the common carriersystem receives track and trace events. The date and time recorded bythe system maintains consistency with the date and time associated withwhere that event occurred (e.g. from GMT to local time of the shipper,local time of the destination location, local time of the sendinglocation, and the like). That is, the date and time may be adjusted tomatch the time zone of the user or other parties.

[0077] The user uses the track and trace function by using the commoncarrier system track and trace user interface. This enables the user toselect criteria against which a search may be conducted. The user hasthe ability to customize how the search results are displayed. The userhas the ability to customize display results on an individual containerbasis or on a “batched” container basis. The common carrier system may“batch” container records. When the common carrier system returns trackand trace information on “batch” records, the user has the ability todrill-down to the container level detail and to drill back up.Furthermore, the user has the ability to ascertain, at glance, where thecontainer is in relation to the activity plan and clear visibility as towhat events have been successfully completed and which were not.

[0078] Referring to FIGS. 4a and 12 a-12 c, by clicking, for example,the track and trace icon 436 of FIG. 4a, the user enables the track andtrace search window as shown in FIG. 12a. The user enters the specificcontainer data in the field 1201 and, by using the drop-down menu 1202,the user identifies the type of data. The type of data may be any of thefollowing: bill of lading number; container number; booking number;carrier booking number; customer reference number; shipper/consigneenumber, date ranges for place of receipt, first load port, finaldischarge port and delivery location; receipt/delivery locations,load/discharge locations, carrier, vessel and voyage number, currentcontainer activities/status and the like. The common carrier interfacedisplays the search results screen as shown in FIG. 12b. If desired, theuser may view a booking summary by clicking on, for example, the word“details” 1203 or track the containers by clicking on the “TrackContainer” button 1204 which links the user to the container plan screenshown in FIG. 12c. Furthermore, the user has the option of customizingthe booking by clicking the “Customize Booking” button 1205.

[0079] Event notification may be submitted to the nominated users usingany of the following technologies: EDI, Email, common carrier interfacepop-up dialogue box and the like. This may be based on the userstechnology. Furthermore, the user may define the rules with respect toevent notification. Table I below shows an example of the events, eventtriggers and event notification as determined by the user.

[0080] The system may, upon the user demand, automatically generatenotices of cargo movement according to the user specification. The eventhandling functionality may be employed to provide notification regardingthe certain track and trace events, track and trace non-events, andcertain business process decisions. The event notification component ofthe common carrier system may reflect the workflow environment wherebyinterested users are notified when an event has occurred, or when onehasn't (e.g. a shipment was expected on a certain day, but is notexpected to arrive until the next day). The user may specify theirtolerances for these events. For example, one user may which to know ifa shipment is late more than six hours, whereas another is more tolerantand a 24 hour delay and notification is acceptable.

[0081] To notify the user when an event has not occurred, the commoncarrier system polls the booking activity plan information periodicallyto identify non-conformances against the booking activity plan, that is,when milestone events (that should have occurred) have not. Eventmessages may contain event code and location information. When thesystem identifies a non-conformance, an event notification isautomatically generated and submitted to nominated entries. Anon-confirmation in this case is deemed to be when the system has notreceived an event message prior to or at the date/time of the eventshould have occurred as defined in the booking activity plan. The commoncarrier system also submits track and trace events notifications whencertain “optional” events are notified to the system, for examplecustoms held and customs release. TABLE I Events Event Trigger EventSource Event Notification Empty container Empty Container Released byCarrier Carrier's system or None pick-up CC System Empty containerArrival of container at Shipper's Carrier's system or None positionedpremises CC System Departure Departure of Container from a LocationCarrier's system or Yes, if not notified CC System to CC System ArrivalArrival of Container at Location Carrier's system or Yes, if notnotified CC System to CC System Loaded on Truck As part of an inlandmove, container has Carrier's system or None been loaded onto a Truck CCSystem Loaded on Rail As part of an inland move, container has Carrier'ssystem or None been loaded onto a train CC System Loaded on Barge Aspart of an inland move, container has Carrier's system or None beenloaded onto a barge CC System Loaded on Container has been loaded onto avessel Carrier's system or None Vessel CC System Discharged fromContainer has been unloaded from Carrier's system or None Vessel vesselCC System Customs Container has cleared customs Carrier's System or YesClearance nominated agent's system or CC System Customs Hold Containerhas been held at Customs Carrier's System or Yes nominated agent'ssystem or CC System Customs Release Container has been released byCustoms Carrier's System or Yes after being held nominated agent'ssystem or CC System Cargo Release Cargo has been released by the CarrierCarrier's system or None CC System Free Time to Containers from timeabout to expire Carrier's system or Yes Expire CC System Free TimeContainer free time has expired Carrier's system or Yes Expired CCSystem

[0082]FIG. 13 illustrates the flow of messages sent and received by thecommon carrier system. EDI may be received in all EDI formats. Carriersmay, for example, send 301 document message types to confirm containerbooking. Carriers may, for example, send document type 315 status eventsto the common carrier system to update container status. Events may be,for example and without limitation, anything from pick up at shipper, toocean voyage through customs clearance to ultimate delivery. Carriersmay send a range of different messages. Finally, the common carriersystem supports but is not limited to EDI, XML, email and the like tosend out received messages to the users.

[0083] Thus, has been described a system that enables domestic and/orinternational transportation users to handle shipping transactionsthrough a single common system substantially through a neutraltransportation portal. The system provides, among other things,transportation users with single point of entry for tracking cargomovements with multiple carriers. The system also gives users access toscheduling, booking requests for booking cargo across several carriersand proactive event notification. Many variation and alterations of theembodiments are of course possible.

We claim:
 1. A system comprising: a common carrier interface enabling auser to create a booking request, submit the booking request to anyentity registered with the system and receive confirmation of thebooking request from the any entity.
 2. The system according to claim 1,wherein the booking request is created from a template stored on thecommon carrier system, wherein the template was created by the userprior to the creation of the booking request.
 3. The system according toclaim 1, wherein the booking request is created from a previouslydrafted booking stored on the common carrier system, wherein the draftedbooking was created by the user or any other user prior to the creationof the booking request.
 4. The system according to claim 3, wherein thepreviously drafted booking was a confirmed booking request that wasconfirmed by at least one of the registered entities prior to the useror the any other user creating the booking request.
 5. The systemaccording to claim 1, wherein the booking request includes a sectionwhich enables the user to request a container be transported, whereinthe container is transported from an inland origin to a vessel, thecontainer is loaded onto the vessel, the container is transported by thevessel to an intermit location, the container is discharged from thevessel and the container is delivered to an inland destination.
 6. Thesystem according to claim 1, wherein the user and the registered entitynegotiated shipping costs prior to the user submitting the bookingrequest.
 7. The system according to claim 1, wherein the user and theregistered entity never negotiated shipping costs prior to the usersubmitting the booking request.
 8. The system according to claim 7,wherein the user is a new customer of the registered entity.
 9. A systemcomprising: a common carrier interface enabling a user to create abooking request, submit the booking request to any entity registeredwith the system and receive confirmation of the booking request from theany entity, wherein the system, responsive to confirmation from theregistered entity to the user and registered entity data, enables theuser to track and trace a container.
 10. The system according to claim9, wherein the user is capable of tracking and tracing multiplecontainers transported by multiple registered entities using the commoncarrier system.
 11. The system according to claim 9, wherein theregistered entities transport goods for the user.
 12. The systemaccording to claim 10, wherein the registered entities transport goodsfor the user.
 13. A system comprising: a common carrier interfaceenabling a user to create a booking request, submit the booking requestto any entity registered with the system and receive confirmation of thebooking request from the any entity, wherein the system, responsive toconfirmation from the registered entity to the user and registeredentity data, generates event notification messages.
 14. The systemaccording to claim 13, wherein the user determines when the systemshould notify the user of an event.
 15. The system according to claim14, wherein the event is a non-event.
 16. The common carrier systemaccording to claim 15, wherein the common carrier system notifies theuser of the non-event after a predetermined time period has lapsed andthe event has not occurred, wherein the user determines thepredetermined time period.